SAP Enterprise Threat Detection, cloud edition
Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊
| Attribute | Value |
|---|---|
| Connector ID | SAPETDAlerts |
| Publisher | SAP |
| Used in Solutions | SAP ETD Cloud |
| Collection Method | CCF |
| Connector Definition Files | SAPETD_connectorDefinition.json |
| DCR Definition Files | SAPETD_DCR.json |
| CCF Configuration | SAPETD_PollerConfig.json |
| CCF Capabilities | OAuth2, Paging |
| Microsoft Learn | View on Learn |
The SAP Enterprise Threat Detection, cloud edition (ETD) data connector enables ingestion of security alerts from ETD into Microsoft Sentinel, supporting cross-correlation, alerting, and threat hunting.
Tables Ingested
This connector ingests data into the following tables:
| Table | Transformations | Ingestion API | Lake-Only |
|---|---|---|---|
SAPETDAlerts_CL |
✓ | ✓ | ✓ |
SAPETDInvestigations_CL |
✓ | ✓ | ✓ |
💡 Tip: Tables with Ingestion API support allow data ingestion via the Azure Monitor Data Collector API, which also enables custom transformations during ingestion.
Permissions
Resource Provider Permissions:
- Workspace (Workspace): Read and Write permissions are required.
- Keys (Workspace): Read permissions to shared keys for the workspace are required. See the documentation to learn more about workspace keys
Custom Permissions:
- Client Id and Client Secret for ETD Retrieval API: Enable API access in ETD.
Setup Instructions
⚠️ Note: These instructions were automatically generated from the connector's user interface definition file using AI and may not be fully accurate. Please verify all configuration steps in the Microsoft Sentinel portal.
Step 1 - Configuration steps for the SAP ETD Audit Retrieval API
Follow the steps provided by SAP see ETD docs. Take a note of the url (Audit Retrieval API URL), uaa.url (User Account and Authentication Server url) and the associated uaa.clientid.
NOTE: You can onboard one or more ETD subaccounts by following the steps provided by SAP see ETD docs. Add a connection for each subaccount.
TIP: Use the shared blog series for additional info.
2. Connect events from SAP ETD to Microsoft Sentinel
Connect using OAuth client credentials ETD connection
When you click the "Add account" button in the portal, a configuration form will open. You'll need to provide:
Account Details
- SAP ETD Client ID (optional): Client ID
- SAP ETD Client Secret (optional): Client Secret
- Authorization server URL (UAA server) (optional): https://your-tenant.authentication.region.hana.ondemand.com/oauth/token
- SAP ETD data retrieval API URL (optional): https://your-etd-cloud-data-retrieval-service.cfapps.region.hana.ondemand.com
💡 Portal-Only Feature: This configuration form is only available in the Microsoft Sentinel portal.
3. ETD accounts
Each row represents a connected ETD account Connector Management Interface
This section is an interactive interface in the Microsoft Sentinel portal that allows you to manage your data collectors.
📊 View Existing Collectors: A management table displays all currently configured data collectors with the following information:
- Data retrieval endpoint
➕ Add New Collector: Click the "Add new collector" button to configure a new data collector (see configuration form below).
🔧 Manage Collectors: Use the actions menu to delete or modify existing collectors.
💡 Portal-Only Feature: This configuration interface is only available when viewing the connector in the Microsoft Sentinel portal. You cannot configure data collectors through this static documentation.
Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊